Hey @duncanmcclean — thanks for this PR. As this issue currently breaks the whole application on our end (all event date ranges are shifted by one day), we’d really appreciate it if this could be merged soon.

An alternative solution would be to set date_format: Y-m-d directly on the field, which seems causing the same issue ☺️ Do you know if this will be addressed by the augmentation change as well?

An alternative solution would be to set date_format: Y-m-d directly on the field, which seems causing the same issue ☺️ Do you know if this will be addressed by the augmentation change as well?

Even when this PR is merged, you shouldn't save date range dates in Y-m-d as Statamic needs the correct date & time in order to convert from your app's timezone (by default, UTC) into your browser's timezone.

I don't understand the "fix". When I select the date 3/21/2026, I expect it to save 3/21/2026 and not 3/20/2026. 🤔 Oddly enough, I'm not even using a range picker here but a single date select. So this PR shouldn't even have any interference with it, but it somehow does.

@MrMooky In v6 everything is stored as a UTC timestamp. If your timezone is Europe/Berlin, you'll see the date stored as 2026-03-20 23:00. You have to make sure, that your app has set a timezone via app.timezone or statamic.system.display_timezone. Antlers will convert the dates back to the correct timezone you would expect.

@MrMooky In v6 everything is stored as a UTC timestamp. If your timezone is Europe/Berlin, you'll see the date stored as 2026-03-20 23:00. You have to make sure, that your app has set a timezone via app.timezone or statamic.system.display_timezone. Antlers will convert the dates back to the correct timezone you would expect.

That's what I did/tried because I read that about the UTC default. The problem is, there are already lots of dates stored and when I change app.timezone from UTC to Europe/Berlin, then old dates (using 00:00) are off by a day. So in my example from before, 3/18/2026 will become 3/17/2026 in the frontend.

Simply saving the entries won't update them it seems and there are 240+ date entries in the existing system. What would the suggest fix be here?

If you upgraded from v5 you should not change your app.timezone.

If you upgraded from v5 you should not change your app.timezone.

I upgraded from v5 and I haven't changed the timezone setting initially. But I noticed the issue and when changing it to Europe/Berlin it would show new dates correctly, but old dates were a day off. When using UTC it's vice-versa. 🤷‍♂️